-
Notifications
You must be signed in to change notification settings - Fork 585
OCPVE-645: add CloudCredential capability #1571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@qJkee: This pull request references OCPVE-645 which is a valid jira issue. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
2e74833 to
0452d03
Compare
d53bf61 to
4e8a5ac
Compare
|
CC @jstuever @dlom can either of you think of issues that might occur with disabling this operator. Is it strictly required for any of the other capabilities to operate? I would have initially proposed that this should only be disabled if all other cloud functionality is disabled but I expect we can be a bit more relaxed here since users could supply their own credentials right? |
Correct. The various components can operate just fine if the required credential secrets are being manually managed by the user. This is logically the equivalent to CCO being enabled in cluster and in manual mode.... at which point it does practically nothing (STS aside). |
|
/retest |
Add CloudCredential capability annotation to cloud credential operator related manifests
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/lgtm QE have validated this, and after some changes, appear to be happy with it. CCO PR looks good to go apart from the API vendor bump. @qJkee If for any reason the PRs for this feature do not merge before the 4.15 branch cut, please let me know |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed, qJkee The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@qJkee: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-config-api-container-v4.15.0-202312042232.p0.gbfea29e.assembly.stream for distgit ose-cluster-config-api. |
No description provided.